This article is half-done without your Comment! *** Please share your thoughts via Comment ***
I request to all Database Professionals,
“Please share your experience through the comments”
GIF reference taken from giphy.com.
Laugh@dbrnd.gif: Should a Database Table always have a Primary Key?
Laugh@dbrnd.gif: Are you Junior DBA ?Laugh@dbrnd.gif: Are you storing Comma Separated List in Database?
-
June 20, 2016 at 11:00 am
I was trying to think in any case, but ateh even in relational tables where the indexation ~ ~ is not important, eh good use key only between the columns that ends up being the pk anyway XD
-
June 20, 2016 at 11:02 am
its choice ,, not always
-
June 20, 2016 at 11:02 am
mostly require a primary key
-
June 21, 2016 at 5:15 am
I think that depend for what purpose you are creating table for. If 90% of times you will be firing query for taking data from the table which is about more than 20% of total data in table then I think primary key wont be used.
For inserts, if primary key is not available then no constraint will be checked while inserting which will speedup the insert.
But having no primary key will have effect on updates and deletes.-
June 21, 2016 at 6:48 amNice comment Jaspreet! I am agree with you.
-
-
June 21, 2016 at 7:07 am
it’s recommended to have a primary key
About Me!
